On mips, 1**np.nan and np.nan**0 may be NaN not 1
authorDebian Science Team <debian-science-maintainers@lists.alioth.debian.org>
Sun, 7 Jul 2024 18:36:37 +0000 (19:36 +0100)
committerRebecca N. Palmer <rebecca_palmer@zoho.com>
Sun, 7 Jul 2024 18:36:37 +0000 (19:36 +0100)
commitdbf954d4e07ab657aad15ab1487a67f5f924da14
tree3386b0b8ad84f2a930ac90a0995f8902d95b6c93
parentf4f38a0d2053e31645c8f5170acb20dd7b74009e
On mips, 1**np.nan and np.nan**0 may be NaN not 1

Done this way not a plain xfail to allow only this difference,
not clearly wrong answers

(The same hardware's "invalid value encountered" warnings,
probably from sNaN/qNaN being reversed, are ignored elsewhere:
d/rules and xfail_tests_nonintel_io.patch)

https://en.wikipedia.org/wiki/NaN#Encoding

Author: Rebecca N. Palmer <rebecca_palmer@zoho.com>
Forwarded: no

Gbp-Pq: Name mips_pow_nan.patch
pandas/tests/arrays/floating/test_arithmetic.py
pandas/tests/arrays/sparse/test_arithmetics.py